Default Gateway hostname changes to avoid issues outlined in GEP-3567.#49
Merged
Merged
Conversation
Before these changes, downstream gateways were being provisioned with listeners which are considered to have overlapping hostnames. This is a result of configuring the `<uuid>.<targetDomain>` hostname on a listener, along with the `[v4|v6].<uuid>.<targetDomain>` hostnames on listeners. When this occurs, Envoy Gateway will disable HTTP2 on the listeners, requiring explicit ALPN configuration via a ClientTrafficPolicy. To make sure we provide users with gateways which support HTTP2 out of the box, the decision was made to no longer configure the gateway with the v4 or v6 prefixed hostnames. These addresses will remain in DNS, responding only with A or AAAA records. In an effort to make it more clear to users which hostnames a gateway will accept, the system now injects default HTTP and HTTPS listeners into gateways created by the user which have the `<uuid>.<targetDomain>` hostname. The user may remove these listeners if they wish. All three DNS addresses will remain in the `Status.Addresses` field of the Gateway, which now makes this field more aligned with the intent defined in the spec. The default listener names are now `default-http` and `default-https`, which will result in the reconfiguration of some gateway resources upon deployment - particularly those maintained via HTTPProxy resources. See: https://gateway-api.sigs.k8s.io/geps/gep-3567/
scotwells
approved these changes
Sep 18, 2025
…in the HTTPProxy reconciler, move the HTTPProxy reconciler to accumulate hostnames based on listeners and their status, instead of addresses.
scotwells
approved these changes
Sep 18, 2025
Base automatically changed from
gateway-api-upgrade
to
integration/proxy-updates
September 19, 2025 15:21
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Before these changes, downstream gateways were being provisioned with listeners which are considered to have overlapping hostnames. This is a result of configuring the
<uuid>.<targetDomain>hostname on a listener, along with the[v4|v6].<uuid>.<targetDomain>hostnames on listeners. When this occurs, Envoy Gateway will disable HTTP2 on the listeners, requiring explicit ALPN configuration via a ClientTrafficPolicy.To make sure we provide users with gateways which support HTTP2 out of the box, the decision was made to no longer configure the gateway with the v4 or v6 prefixed hostnames. These addresses will remain in DNS, responding only with A or AAAA records.
In an effort to make it more clear to users which hostnames a gateway will accept, the system now injects default HTTP and HTTPS listeners into gateways created by the user which have the
<uuid>.<targetDomain>hostname. The user may remove these listeners if they wish. All three DNS addresses will remain in theStatus.Addressesfield of the Gateway, which now makes this field more aligned with the intent defined in the spec.The default listener names are now
default-httpanddefault-https, which will result in the reconfiguration of some gateway resources upon deployment - particularly those maintained via HTTPProxy resources.See: https://gateway-api.sigs.k8s.io/geps/gep-3567/
Related work: